This dependency bump is motivated by seeking to get rid of outdated
nan, which was an indirect dependency via keytar. Dropping nan should
hopefully allow compiling native C/C++ code against newer and newer
versions of NodeJS and Electron -- "hopefully".

This version of keytar drops its dependency on nan, instead using
"N-API", now officially renamed to "Node-API". Hopefully this means
it will not need changes to maintain forward-compatibility with future
versions of NodeJS and Electron -- "hopefully."

So, there may also be benefits for upgrading to newer versions of
Electron -- I haven't tested this, I just want to be able to bootstrap
Pulsar core repo on newer system versions of NodeJS, however
irrelevant system NodeJS version may be to final execution in
Electron.

...

This is the latest, and final upstream release of atom/node-keytar;
The upstream repository is now archived.

If we want to see changes in keytar beyond this, we must search for a
suitable, existing fork, or create one ourselves.

This is for Python 3.12+ compatibility in older node-gyp

Switches superstring indirect dependency to Pulsar's fork as well

Uses lockfile v1, which ppm (npm 6) is more compatible with

Also update to a commit of whats-my-line where superstring
is specified as a tarball URL, not a git URL.

Otherwise, no changes.

Just using a simpler format (tarballs), which are quicker
to fetch and quicker to install than git URL dependencies,
as well as being just a lot simpler to deal with under the hood.

This is just the commit from *after merging* the whats-my-line PR
that specified superstring as a tarball URL rather than as a git URL.

No code changed, this just points to the merge commit after merging,
instead of the PR branch tip pre-merge.

(For the benefit of folks who spelunk through the commit histories.
This is a slightly tidier landmark in the whats-my-line repo
to point to: a merge commit into `master` branch,
rather than a random-looking pre-merge commit. No change otherwise.)